Skip to content

feat(extensions): configure installed platform extensions - #49

Open
korolevpavel wants to merge 2 commits into
alkoleft:masterfrom
korolevpavel:feat/issue-43-installed-extension
Open

feat(extensions): configure installed platform extensions#49
korolevpavel wants to merge 2 commits into
alkoleft:masterfrom
korolevpavel:feat/issue-43-installed-extension

Conversation

@korolevpavel

Copy link
Copy Markdown
Contributor

Closes #43.

Adds CLI-only repeatable extensions --extension <PLATFORM_NAME> for installed extensions not represented by source-sets. It is mutually exclusive with --name, preserves direct platform names/order, validates invalid selectors before dispatch, and leaves MCP unchanged.

Verification:

  • cargo test --test cli_extensions (9 passed)
  • cargo fmt --all -- --check
  • cargo check
  • independent Rust review and scoped re-review clean.

Known baseline: unrelated unused-variable warning in tool_extension.rs.

- add repeatable CLI-only --extension selector with validation\n- preserve direct platform names and ordering when forwarding to ibcmd\n- document source-set and installed-extension selection workflows
- render direct extension selector failures before dispatch\n- cover text and JSON validation output without ibcmd execution\n- document installed extension selection in skill references
@coderabbitai

coderabbitai Bot commented Jul 26, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@korolevpavel, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 27 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f17c8ff7-2137-4f6f-aabc-6a2a91e4afe1

📥 Commits

Reviewing files that changed from the base of the PR and between d612e2d and cf9f6e6.

📒 Files selected for processing (10)
  • SKILL/SKILL.md
  • SKILL/references/command-selection.md
  • SKILL/references/config-and-backends.md
  • SKILL/references/project-workflows.md
  • docs/CAPABILITIES.md
  • src/cli/args.rs
  • src/cli/execute.rs
  • src/use_cases/configure_extensions.rs
  • src/use_cases/request.rs
  • tests/cli_extensions.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(extensions): configure an installed extension absent from source-sets

1 participant